System to provide a security technology and management portal

ABSTRACT

A system to facilitate management of surveillance devices, that are distributed over a monitored region, through a geographic information (GI) portal, having GI storage to store map data defining a geographic map of the monitored region. A GI manager unit (GIMU) to record, in the GI storage, asset position information with regarding locations for assets of interest within the monitored region. The GIMU obtains, from a remote surveillance device (SD) database, device-related records. The GIMU obtains, from a remote network (NW) database, network-related records. The SD and NW databases are maintained and managed separately from the GI database by one or more independent management units. A display presents a geographic map of the monitored region with device markers and network links illustrated thereon.

BACKGROUND OF THE INVENTION

The subject matter herein relates generally to systems and methods tofacilitate management of surveillance devices that are distributed overa monitored region.

Numerous surveillance systems exist today that include a large number ofsurveillance devices distributed over a wide area. The surveillancedevices may generally include video equipment, still images cameras,motion monitoring equipment, temperature sensors, water sensors and thelike which collect data (video, images, etc.) for storage in a databaseor a digital video recorder (DVR).

More recently, municipal services and agencies have become interested inhaving surveillance devices installed over all or portions of region(s)for which the municipality or agency is responsible. For example, policedepartments are having security cameras installed on highways and atintersections to monitor whether vehicles comply with speed limits andstop lights. Utility companies are become interested in having camerasand other monitoring equipment installed to monitor utility property(e.g., power grids, power stations, water treatment equipment, sewagesystems, etc.). The surveillance devices are installed on or at desiredlocations relative to property owned, leased or controlled by themunicipal service and/or agency. The surveillance devices are coupled tonetwork devices that transmit recorded surveillance data to the desiredstorage equipment.

Heretofore, numerous separate and independent companies and serviceswere contracted by the municipality or agency to monitor, manage andmaintain the various types of equipment within the surveillance system.For example, one company may be engaged to install part or all of thedevices, while a separate company may be engaged to perform maintenance.Also yet a third company may be hired to manage operation of videodevices and storage of video on DVRs, while a separate fourth companywas hired to manage operation of the network communications devices thatconveyed the collected data to storage equipment. A separate company maybe hired to manage operation of non-video surveillance equipment, suchas motion sensors, speed guns, still image cameras and the like.

In the past, installation engineers have experienced problems whendetermining where specifically to install surveillance devices. Theengineer's base installation on source plan documents that show thelocations of property (e.g., utility poles, etc.) on which thesurveillance devices are to be installed. However, the installationengineer may arrive at an installation site, only to learn that they donot have complete or correct information regarding the property wherethe security and network equipment is to be installed. For example, whena camera is to be installed on a utility pole, the utility pole may notbe at the particular coordinates where the installation engineerexpected it. Also, the engineer may arrive at a location without all ofthe necessary source documentation needed to complete installation(e.g., no engineering drawings, specifications for the wrong securitydevice, invalid network operating parameters (channel or frequencysettings) that do not link to other existing devices, and the like. Oncea security device is installed, there is no convenient manner by whichthe engineer can enter the exact coordinates of the security device inconnection with the source plan documents showing the utility property.

In the past, maintenance engineers have also experienced problems indetermining which specific equipment to repair or perform periodicmaintenance. The maintenance engineer may arrive at a site where theequipment is thought to be installed, only to learn that the equipmentis not at the expected specific location. For example, an engineeringdrawing of the region may show a camera to be on a utility pole locatedon one side of a street or located at one corner of an intersection.However, when the engineer arrives to perform the maintenance, they maylearn that the only camera in the area is on the opposite side of thestreet or at a different corner of the intersection. This causesproblems and confusion as to whether they are at the correct location orif the drawings are simply incorrect.

Moreover, as city wide wireless video systems are being engineered,deployed, and managed, comprehensive documentation is not being created.Also, the documentation being created may not be complete as to thesystem architecture. For example, the documentation is not maintained,nor updated, for a complete system design extending from start tofinish, nor covering snap shot detail layouts in graphic displays.Instead, each separate company or service provider only creates and/ormaintains documentation related to their corresponding subset ofresponsibilities. For example, the company overseeing the networkmanagement sub-system only creates and maintains documentation regardingthe communications sub-system. Other companies only create and maintaindocuments regarding the products that they install, maintain or manage.Manufacturers of individual devices do not create, nor maintain, systemwide documents, while integration service providers do not create, normaintain, product specifications.

Hence, multiple separate documents exist that describe only limitedportions of an overall system. The source plan or engineering documents,that describe the property locations, do not contain information aboutthe surveillance devices. Specifications for the surveillance devicesare not correlated to the particular physical location of thesurveillance device in the monitored region. Warrantee and servicerecords are not correlated with the particular physical location of thesurveillance.

A need remains for a system that correlates physical locations ofdevices to a map, identifies each device, illustrates communicationspaths, presents system status information, enables remote control overthe devices and affords ready access to specifications, warrantee andservice records.

BRIEF DESCRIPTION OF THE INVENTION

In one embodiment, a system to facilitate management of surveillancedevices, that are distributed over a monitored region, through ageographic information (GI) portal, is provided having GI storage tostore map data defining a geographic map of the monitored region inwhich assets of interest are located and surveillance devices (SDs) areinstalled relative to the assets of interest. A GI manager unit (GIMU)is provided to create and store surveillance device related (SDR)objects in the GI storage, each of the SDR objects uniquely associatedwith one of the SDs, the GIMU mapping the SDR objects to surveillancedevice specific content. The surveillance device specific contentincludes at least one of the SD position information regarding alocation of the corresponding surveillance device in the monitoredregion, the asset position information regarding a location for thecorresponding asset with respect to which the SD is installed, the SDdata collected by the corresponding SD and/or the SD documentationdescribing at least one of installation, operation and maintenance ofthe corresponding SD. A display presents a geographic map of themonitored region with device markers illustrated thereon. The devicemarkers indicate positions of the surveillance devices relative to thegeographic map, the device markers mapped to the SDR objects. A userinterface permits a user to select from the surveillance devices bychoosing the corresponding device markers. The GIMU makes available tothe user, the device content associated with the SDR object for theselected surveillance device.

In another embodiment, a method is provided to facilitate management ofsecurity devices that are distributed over a monitored area, through ageographic information (GI) portal, the method storing, map data in a GIstorage. The map data defines a geographic map of the monitored regionin which assets of interest are located and surveillance devices (SDs)are installed relative to the assets of interest. The method creates andstores surveillance device related (SDR) objects in the GI storage, eachof the SDR objects uniquely associated with one of the SDs. The methodfurther maps the SDR objects to surveillance device specific contentthat includes at least one of the SD position information regarding alocation of the corresponding surveillance device in the monitoredregion, the asset position information regarding a location for thecorresponding asset with respect to which the SD is installed, the SDdata collected by the corresponding SD and/or SD documentationdescribing at least one of installation, operation and maintenance ofthe corresponding SD. The method presents on a display a geographic mapof the monitored region with device markers and network linksillustrated thereon. The device markers indicate positions of securitydevices relative to the geographic map, the device markers mapped to theSDR objects. The method permits the user to select, through a graphicaluser interface, from the surveillance devices by choosing thecorresponding device markers. The method makes available to the userdevice content associated with the SDR object for the selectedsurveillance device.

In an embodiment, a system to facilitate management of network devices,that are distributed over a monitored region, through a geographicinformation (GI) portal, is provided having GI storage to store map datadefining a geographic map of the monitored region in which assets ofinterest are located and network devices (NDs) are installed relative tothe assets of interest. A GI manager unit (GIMU) is provided to createand store network device related (NDR) objects in the GI storage, eachof the NDR objects uniquely associated with one of the NDs, the GIMUmapping the NDR objects to network device specific content. The networkdevice specific content to include at least one of the ND positioninformation regarding a location of the corresponding network device inthe monitored region, the asset position information regarding alocation for the corresponding asset with respect to which the ND isinstalled, the ND data collected by the corresponding ND and/or the NDdocumentation describing at least one of installation, operation andmaintenance of the corresponding ND. A display presents a geographic mapof the monitored region with device markers and network linksillustrated thereon. The device markers indicate positions of thenetwork devices relative to the geographic map, the network linksillustrating communications paths between network devices, the devicemarkers and network links mapped to the NDR objects. A user interfacepermits a user to select from the network devices or network links bychoosing the corresponding device markers or network links. The GIMUmakes available to the user, the device content associated with the NDRobject for the selected network device or network link.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a system formed in accordance with an embodiment ofthe present invention.

FIG. 2 illustrates a screen shot of a window presented on the userinterface of FIG. 1.

FIG. 3 illustrates the window of FIG. 2 with the geographic map zoomedin closer to a particular monitored sub-region in accordance with anembodiment of the present invention.

FIG. 4 illustrates a window with the geographic map zoomed to amonitored sub-region in accordance with an embodiment of the presentinvention.

FIG. 5 illustrates a map with a video pop up screen overlaid thereon fora selected camera in accordance with an embodiment of the presentinvention.

FIG. 6 illustrates a map on which selected nodes have been changed to anoffline state in accordance with an embodiment of the present invention.

FIG. 7 illustrates a map with a background blending window in accordancewith an embodiment of the present invention.

FIG. 8 illustrates a map with an identification window in accordancewith an embodiment of the present invention.

FIG. 9 illustrates a block diagram of a processing sequence carried outin accordance with an embodiment to collect, store and manage SD and NDcontent.

FIG. 10 illustrates a processing sequence carried out in accordance withan embodiment for updating content associated with surveillance devices.

FIG. 11 illustrates a processing sequence carried out in accordance withan embodiment for updating content associated with network devices.

FIG. 12 illustrates a process carried out while a user is reviewinggeographic information, device markers and network links on a graphicuser interface and selecting various devices to manage.

FIG. 13 illustrates, in more detail, the process performed when the userwishes to select or modify an SD or ND marker, a network link or anarea.

DETAILED DESCRIPTION OF THE INVENTION

In accordance with embodiments herein, systems and methods are providedthat afford real time “in the cloud” managed data. Cameras and othersurveillance devices are positioned throughout a monitored area onassets such as public utility/city owned poles and buildings. A networkis created to connect the surveillance devices to a central, singlelocation from which real time events are managed. The network may bechanged constantly, and accordingly, the systems and methods providedherein enable such changes to be documented easily. The systems andmethods provided herein also ensure centralized control over changes tothe network and to the documentation describing network changes. Thesystems and methods provided herein gather data for every architecturallayer and enable input of such data to a common storage and providesearch tools are able to readily and quickly search the storage fordesired information. The systems and methods provided herein affordadministrative controls over the documentation to avoid mistakes. Forexample, the data, controlled by engineers and service organizations,may be placed on a server that is accessible by individuals who may needto utilize these documents, thereby ensuring central control over thedata.

By way of example, customers may include city, state and county serviceswho utilize embodiments hereof as a centralized system to monitorequipment and other asserts that are scattered over a wide area.Emergency management services may also utilize embodiments hereof tomonitor emergency systems. Other examples of service customers mayinclude any public or private entity that has assets deployed over alarge area or has a large number of assets that warrant monitoring.Embodiments hereof may be used to facilitate management of, among otherthings, warranty dates, service schedules, maintenance histories and thelike. Embodiments described herein avoid the need to make multiplerevisions of paper documents, and instead afford a paperless documentmanagement system with up-to-date revisions and the ability to send andreceive documents to all or multiple participants in very little time.Optionally, customers may be charged for edits made to documents orchanges to the system.

FIG. 1 illustrates a system formed in accordance with an embodiment ofthe present invention. The system 100 facilitates management ofsurveillance devices 115-117, that are distributed over a monitoredregion 110. The system 100 utilizes a geographic information (GI) portalto facilitate device and document management.

The system 100 comprises GI storage 186 that store various types ofdata, objects, and the like. The GI storage 186 may be located at onelocation or multiple locations that are interconnected over the internetor operated as a cloud network of storage space. For example, the GIstorage 186 may be all or partially on a 3^(rd) party server that leasesspace to users. The GI storage 186 includes one or more storage devices181-183, that may be similar types of storage or different types ofstorage. For example, the storage devices 181-183 may be servers, flashdrives, RAM, ROM, disc, RAID, and the like.

The system 100 accumulates documentation describing multiple differentlayers of information. The layers include a base layer, an asset orproperty layer, a surveillance device layer, a network layer, amaintenance layer, an operational layer, and the like. The base layerincludes map data describing a geographic map of the region. The assetlayer includes documents that describe each asset of interest to thecustomer (e.g., municipality, service private business, etc.), includingGPS coordinates or position, the asset type, asset attributes and thelike. The surveillance device layer contains documents that describe thedevices, including installation manuals, specifications, operationparameters, device attributes, warrantee and the like. The network layercontains documents that describe the network devices, includinginstallation, specification, operation parameters, network attributes,warrantees and the like. The maintenance layer includes information thatdescribes the maintenance history for the devices, network, and assets.The operational layer includes information that describes the status,condition and operating parameters of the devices and network.

The monitored region 110 may represent all or a portion of a state,county, city, community, or other metropolitan area. The monitoredregion may correspond to all or a portion of a region of interest to apublic service, such as a fire department district, a police district, awater or sewage district, an electrical utility grid, college campus,school grounds, school district and the like. Optionally, the monitoredregion may represent a region of private interest to a commercialbusiness, such as an office campus, a manufacturing plant, a mine, adrilling rig, a number of buildings owned or operated by a business andthe like. The region of interest may not be one contiguous area, butinstead may include multiple separate physical areas.

The monitored region 110 includes assets 115-117 that are distributedacross the monitored region 110. Assets 115-17 will vary depending uponthe nature of the customer enterprise. The assets may represent any typeof physical property, equipment or structure that is owned, leased orotherwise available for use by a customer of the system 100. Forexample, the assets 115-117 may include utility poles, traffic lightstructures, tunnels, water pumps, electrical transformers, powerstations, power lines, storm sewers, road intersections, highwaysegments, railroad segments, railroad switching stations, buildings,manufacturing plants, power plants, warehouses, residential homes,drilling rigs, mines, vehicles, and the like.

A collection of surveillance and network devices 120-126 are positionedat desired locations throughout the monitored region 110. The type ofdevices will vary based on the type of monitored region and user. Forexample, the network and surveillance devices 120-126 may include videocameras, still image cameras, audio recorders, motion sensors,temperature sensors, water sensors, gas sensors, security sensors,switches, and other surveillance related devices. The surveillancedevices 120-123 collect surveillance device content such as video, stillimages, audio, temperature data, motion data, switch state,environmental conditions and other data. As one example, a networkdevice 124-126 may be located at each asset 115-117, while one or moresurveillance devices 120-123 may also be located at each asset 115-117.The surveillance devices 120-123 are communicatively coupled to thenetwork devices 124-126 such that data, commands, status, conditions andother information may be passed bi-directionally there between. In theexample of FIG. 1, the surveillance device 120 bi-directionally passesdata, commands, status and other information through the network device124 to the overall network. The surveillance device 121 bi-directionallypasses surveillance device content data, commands, status, conditionsand other information through the network device 125 to the overallnetwork. The surveillance devices 122-123 bi-directionally passsurveillance device content data, commands, status, conditions and otherinformation through the network device 126 to the overall network.

The network devices 124-126 may communicate over various wired and/orwireless links 130-138 bidirectionally transmit to surveillance devicecontent and network device content. The links 130-138 may be one type, asubset of types or all may be used in one implementation. The networkdevices 124-126 communicate with one another over device to device links130. The network devices 124-126 communicate with manager units 150-152over one or more types of links, such as a local area or wide areanetwork (LAN or WAN) link 132, a wireless link 134 to a cellular tower139, an Internet link 138 and the like. The network devices 124-126 maycommunicate with routers 140 that in turn are connected, over routerlinks 135, to a LAN, a WAN, the Internet and the like. The devicemanager unit (DMU) 150 may communicate over a LAN or WAN link 132 withdifferent network devices 125-126, while network manager unit (NMU) 151communicates over a cellular link 134 with different network devices126. A surveillance device (SD) unit 152 may communicate over link 135through router 140 with different network devices 124 and 126. Oneexample of the surveillance device may be a video or still image camera,and thus item 152 is also referred to as VMU or SD manager unit. Whilenot shown, each of the network devices 124-126 may be configured tocommunicate with each of the manager units 150-152.

The links 130-138 between the network devices 124-126 and the managerunits 150-152 may be through various intermediate equipment. The networkdevices 124-126 may represent wired or wireless communications equipmentthat are configured to utilize various transmission medium, such asdifferent ranges of the radio frequency spectrum, microwave spectrum,optical transmissions, satellite transmissions, and the like. Thenetwork devices 124-126 may include RF transceivers to transmit andreceive RF transmissions. The network devices 124-126 may includecellular transceivers to transmit and receive utilizing cellular towersand protocols. The network devices 124-126 may include equipment thatcommunicates based on line-of-sight transmissions such as with GPSsystems. The surveillance and network devices 120-126 may be tunable todifferent channels, frequency spectrums and the like. The networkdevices 124-126 may include memory to temporarily buffer data, commands,status, and other information generated by the security device(s)120-123.

The SD manager unit or VMU 152 monitors, maintains and manages videorelated surveillance devices 120-123. For example, the VMU 152 maymonitor and/or receive surveillance device content, such as streamingvideo and/or still images from cameras located throughout the monitoredregion 110. The VMU 152 may adjust the status (e.g., condition,direction, zoom, camera settings) and other characteristics of thecameras. The VMU 152 may determine and change which digital videorecording (DVR) equipment receive video data from a camera. The VMU 152also manages operation of the DVR equipment.

The NMU 151 monitors, manages and maintains the network devices 124-126.For example, NMU 151 monitors various characteristics related totransmissions between the network devices 124-126 as well ascommunication to and from the network devices 124-126 and other networkequipment. For example, the monitor characteristics may include signalstrength, bandwidth usage, unused bandwidth, and the like. The NMU mayadjust the status, conditions and other characteristics of the networkdevices 124-126. For example, the NMU 151 may take an individual networkdevice online or offline. Also, the NMU 151 may change which networkdevices communicate directly with one another. The NMU 151 may alsoreadjust bandwidth and/or the number of channels permitted to be used byeach network device 124-126.

The NWU 151 communicates with the network devices installed in themonitored region. The NWU 151 collects network device content (includingstatus, and condition data) from the network devices and records thenetwork device content (including status and condition data) in the NWdatabase 161. The NMU 151 communicates with the network (NW) database161 to manage and maintain network device content stored in the NWdatabase 161. Among other things, the NMU 151 may update the NW database161 with NW position information or tags 161B associated with eachnetwork device 124-126 to identify the physical location or GPScoordinates of the network device 124-126 within the monitored region110. By way of example, the NW database 161 may be organized intomultiple segments of content 161 a, each of which is associated with acorresponding network device 124-126. The network device content 161 amay contain and map together various types of information, such asspecification documents, addressing information, unique name andidentification information, service history and records and the like.The NW database 161 may map NDR objects to network device content thatincludes at least the following i) ND position information regarding alocation of the corresponding network device in the monitored region,ii) asset position information regarding a location for thecorresponding asset with respect to which the ND is installed, iii) NDdata collected by the corresponding ND, and iv) ND documentationdescribing at least one of installation, operation and maintenance ofthe corresponding ND.

The device manager unit (DMU) 150 monitors, maintains and manages othertypes of devices, which may not be considered video or network relateddevices. For example, the DMU 150 may manage various security sensors,switches, locks and the like. The DMU 150 communicates with thesurveillance devices installed in the monitored region. The DMU 150collects security, status, and condition data from the surveillancedevices and records the security, status and condition data in thedatabase 160. The DMU 150 interacts with a device database 160 to storedevice data, as well as status, condition information and the like. Thedevice database 160 may also store various documents related to thedevices managed by the DMU 150. The device database 160 may be organizedinto multiple segments of content 160 a that include, among otherthings, position information or tags 160 b that identify the physicallocation (e.g., intersection or GPS coordinates) of the correspondingdevice. The device database 160 and the DMU 150 also communicate withthe Internet (as illustrated by the links 170.)

Each of the manager units 150-152, and databases 160-162 may be coupledto the Internet, as indicated by the various connections to 170. Thedatabase links 160 c-162 c affords direct access to the content of thedatabases 160-162 by other manager units coupled to the Internet throughcloud 170. For example, remote devices such as the GI manager unit 180may directly access the databases 160-162 to obtain records and/or datatherefrom. Alternatively, the GI manager unit 180 may request, from thecorresponding manager unit 150-152, a particular type of information,such as data, records and the like, which are then obtained by thecorresponding manager unit 150-152 from the corresponding database160-162.

The security data (SD) database 162, network (NW) database 161 anddevice database 160 are maintained and managed by one or moreindependent management units, such as DMU 150, NMU 151 and VMU 152. TheDMU 150, NMU 151 and VMU 152 maintain and manage the device, SD and NWdatabases 160-162 separately from the GI storage 186. For example, theSD database 162 may store surveillance device content such as images,video data, and other types of security data, as well as status andcondition information regarding the corresponding surveillance devices.The SD database 162 stores NDR content 162 a associated with SDsinstalled throughout the monitored region. The content 162 a includesattributes that define operation, performance and capabilities of thecorresponding devices. The database 162 stores objects associated withsurveillance devices installed throughout the monitored region, theobjects including attributes that define operation, performance andcapabilities of the corresponding surveillance devices. The SDR objects162 b are mapped to surveillance device content such as i) SD positioninformation regarding a location of the corresponding surveillancedevice in the monitored region, ii) asset position information regardinga location for the corresponding asset with respect to which the SD isinstalled, iii) SD data collected by the corresponding SD, and iv) SDdocumentation describing at least one of installation, operation andmaintenance of the corresponding SD

The GI storage 186 stores, among other things, map data 191 defining ageographic map of the monitored region 110. The GI storage 186 stores SDand ND content 192 such as data, documents, status, condition,coordinates and other information in connection with the various layers(e.g., base, asset, device, network, and surveillance layers). The GIstorage 186 is managed by a GI manager unit (GIMU) 180 to facilitatemanagement of the network and surveillance devices and links. The GIMU180 manages storage of the various content 192 and information in anobject oriented architecture that correlates each surveillance andnetwork device to an object 193 which is then mapped to content 192,such as a device physical location 194, an asset location 195,video/image content 196, data 197, documents 198, status 199, conditionand other information. For example, the GIMU 180 may store certain typesof information and documents 231 in the GI storage 186 that is obtainedduring installation of assets, then add other content duringinstallation of network and surveillance devices, and other informationand documents thereafter. The map data, device related content and otherinformation are periodically accessed for updating within the GI storage186 and to be provided when selected by users at the user interfaces 254and at portable wireless devices 185.

The GIMU 180 records, in the GI storage 186, asset position information233 (e.g., coordinates) regarding locations of assets 115-117 that areof interest within the monitored region 110. The GIMU 180 accesses SDdatabase 162 to obtain device-related content 162 a. The GIMU 180 storesall or portions of the device related content 162 a in the GI storage186. The device related content 162 a is mapped to SDR objects 235associated with the surveillance devices 120-123 installed in themonitored region 110. The device related content 162 a may includeposition information or tags 237 to the objects 235, identifying alocation of the corresponding surveillance devices 120-123 in themonitored region 110. The device related content 162 a may includedocuments and attributes that define operation, performance andcapabilities of the corresponding surveillance devices. The attributesmay represent device identification information, device-generatedcontent, device-status information, device-service history, and thelike.

The GIMU 180 also accesses the NW database 161 to obtain network-relatedcontent 161 a for network devices 124-126 that are of interest. The GIMU180 stores the network related content 161 a in the GI storage 186. Thenetwork-related content 161 a and position information or tags 161 b,that identify a location of the corresponding network devices 124-126that are installed over the monitored region 110, are mapped to NDRobjects 193. The network-related content 161 a includes documents andattributes that define operation, performance and capabilities of thecorresponding network devices. The attributes include network deviceidentification information, network device-generated content, networkdevice-status information and network device-service history.

The GI storage 186 stores as content 192, among other things, identityinformation about each surveillance and network device, such as cameraname, type, number, IP address, a last viewing direction, a descriptionof the street or intersection at which the device is located, MACaddress, radio node number, ON/OFF time, ON/OFF status, signal strength,last service date, preset views, present view, utility pole number, poletype and the like, all of which are examples of surveillance and networkdevice content. The GI storage 186 also stores, as content 192, sourcedocuments associated with the monitored region 110, the assets 115-117,and the devices 120-126. The source documents may include one or more ofdocuments used by emergency services personnel, water services, sewageservices, waste management, utilities and engineering personnel, all ofwhich are examples of surveillance and network device content. Forexample, these documents may include engineering drawings or a floorplan for one or more buildings and/or physical plans for assets 115-117in the monitored region 110 (e.g. a pole plan, a power line griddiagram, water line plan, engineering diagrams, and the like). Thesedocuments may include engineering documents, assembly documentsregarding how to install devices, device specifications, and the like.Device-related documents may contain device specific information about acorresponding type of device, including device specification,operational parameters, maintenance information, installationinstructions and repair information. Network-related documents maycontain information about a corresponding type of network device,including device specification, cooperational parameters, maintenanceinformation, installation instructions and repair information.

The system 100 includes one or more user interfaces 254 that eachincludes a display 256. The display 256 presents to a geographic map ofthe monitored region 110 where the map is overlaid with indiciarepresenting surveillance device markers, network device markers andnetwork links to for a geographic information portal. The device markersindicate position, direction, field of view, type and status of thesurveillance devices 120-123 relative to the geographic map. The networklink indicia indicate status of communications links between networkdevices, a direction of communication, the status of the link, and thelike. The user interface 254 permits a user to select from the networkdevices, surveillance devices and network links. The GIMU 180 makesavailable to the user the link and device related content for theselected device or link. The GIMU 180 accesses stored content based onselections by the user at interface 254 to display various informationto the user. Examples of GUI displays are shown in FIGS. 2-8 for the GIportal.

FIG. 2 illustrates a screen shot of a window 200 presented on the userinterface 195. The window 200 includes a map area 202, a network controlarea 204, and a map tool bar 206. The map area 202 illustrates ageographic map 210 of all or a portion of the monitored region 110. Thegeographic map 210 illustrates roads and other geographic landmarkswithin the monitored region 110. The map tool bar 206 includes a varietyof icons that may be selected to adjust the displayed portion of thegeographic map 210 such as the zoom icon 212, pan out icon 214, selecticon 216, device identity icon 220, pan icon 222 and the like. Thedevice identity icon (DII) 220 is selected to obtain detailedinformation about a particular device. The zoom icon 212 and pan outicon 214 are used to adjust the displayed portion of the map. The selecticon 216 is used to mark a device of interest. When the pan icon 222 isselected, the user is able to pan to different areas of the map that arenot yet visible on the display by clicking and dragging.

The network control area 204 may be switched between different controlmenus, namely a layer menu, a tools menu and a search menu. The networkcontrol area 204 in FIG. 2 is shown with the “layer” menu selected. Inthe layer menu, a layer structure is presented that includes one or moreouter and sub-layers. For example, the outer layer may designatedifferent geographic sub-regions such as cities, counties, municipalzones, campuses, etc. Below the outer layer, one or more sub-layers arepresented for different types of equipment within the networkarchitecture. For example, the equipment sub-layer may include a camerasub-header, a radio-link sub-header, a backhaul information sub-headerand a backhaul link sub-header. The camera sub-header may have one ormore sub-categories of devices, such as for fixed cameras, stillcameras, PTZ (pan-tilt-zoom) cameras and the like. The radio linksub-layer may list each radio link available (online or offline) in thenetwork. The radio sub-layer includes another sub-layer that separates“radios with cameras” from “radios only” (without cameras). The “radioswith cameras” sub-header then lists each radio by a unique ID (e.g.,BA100, BA200, etc) that is connected to a camera. The “backhaulinformation” sub-header identifies each network device used to conveythe backhaul information. The “backhaul link” sub-header indicates thestatus of the backhaul link, such as signal quality, capacity used,capacity available, etc.

By navigating through the architecture layers in the network controlarea 204, the user is able to access different information in thearchitecture of the network, including each device therein and eachcommunications link. The user is then afforded the option to selectindividual devices and obtain a large amount of information regardingthe selected device(s).

FIG. 3 illustrates the window 200 but with the geographic map zoomed incloser to a particular monitored sub-region 302. The map area 202illustrates network and surveillance devices that are located in thesub-region 302. The sub-region 302 illustrates a group of cameras thatare individually labeled with unique IDs, namely F32, F29, P24, and P27.Information is added next to each camera name, such as the intersectionwhere the camera is located (e.g., camera F29 is at the intersection ofFactory Street and 7^(th) Street). The sub-region 302 also illustratesnodes such as N12 where a repeater radio may be located. The sub-region302 also illustrates and labels radios located at buildings (e.g.,Sealing Bldg Radio).

The sub-region 302 also illustrates communications links between theequipment. The communications links may be shown in different colors,line thicknesses, line types, etc., to indicate the type of link. Forexample, a thick blue line may be shown for communications links of onetype. A thin red line, dashed line, etc. may be shown for communicationslinks that are a different type. For example, a thick blue line is shownbetween the cameras F29 and P24, between the cameras P24 and P27, andbetween camera P24 and node N12. Thick blue lines for other links arealso shown to extend from node N12 off the edge of the viewable portionof the map, as well as from camera F23 off the edge and from camera p27off the edge.

A communications link is shown in a thin red line extending from theSealy Building Radio off the edge of the map. The link is shown in athin red line from the Sealy Building Radio to indicate that this linkis a different type. The user may select a radio by choosing the radiofrom the network control area 204 or by double-clicking on the node inthe map. Once the radio is chosen, a pop up window is presented topermit the user to change a state of a radio between off line and online by toggling a corresponding status flag.

FIG. 4 illustrates the window 200 but with the geographic map zoomed toa monitored sub-region 402. The sub-region 402 includes a group of nodeshaving cameras and radios. The window 200 includes communications linkstatus (CLS) indicia 404 extending between the radios that arebi-directionally communicating with one another. The CLS indicia 404indicates a status of a communications link, such as on-line, off-line,experiencing non-fatal errors, operating at least partially outside ofparameter limits, and the like. For example, when two radios are on-lineand the communications link is operating within acceptable limits, theCLS indicia 404 may be shown as a thick blue/green dashed line with thedashes moving in the direction in which communications are traveling.Alternatively, when a radio is off line and/or is operating outsidesystem parameter limits, the CLS indicia 404 changes to reflect thisstatus change.

The window 200 illustrates camera condition (CC) indicia 406 associatedwith each camera. The CC indicia 406 may indicate the direction in whicheach camera is pointed with respect to the geographic map. For example,the camera at node P30 is directed substantially to the west, while thecamera at F28 is directed substantially to the east. The camera at nodeF81 is directed to the northwest and conveys video data to the SealyBuilding Radio via communicates links between radios at nodes N19 andN18, F28 and F27. The CLS indicia 404 and CC indicia 406 are turned onand off by selecting the “tools” layer in the network control area 204.

FIG. 5 illustrates the map 202 with a video pop up screen 502 overlaidthereon for a selected camera at node P32. The user may select thecamera at node P32 by clicking on the node in the map or by clicking onthe camera name in the network control area 204. Optionally, the screen502 may pop up when the user hovers a “mouse” icon over a particularnode. The video pop up screen 502 shows a real-time video 510 or stillimage of the current video/image data generated by the camera along withheader information 512. The CC indicia 504 illustrates a cone extendingthe direction 506 in which the camera is directed, thereby facilitatingthe user's understanding of what area is within the cameras field ofview that is shown in the video pop up screen 502. The CC indicia 504may have a dark border to denote a fixed camera or lack dark border todenote a camera with pan-zoom-tilt.

When the camera is a pan-zoom-tilt (PZT) type camera, the user mayselect the camera by clicking on the node and then change the pan, zoomand/or tilt thereof through device operation fields. The video pop upscreen 502 may include a camera direction slide bar 514 below the videoarea. The user may click and drag the tab 516 for the camera directionbar 514 which causes the camera to be rotated. Optionally, the video popup screen 502 may also include a zoom control bar 518 and a tilt controlbar 520. When the user clicks and drags the tabs in the zoom and/or tiltcontrol bar 518 and 520, this causes the cameras to zoom and tilt,respectively.

Optionally, the network control area 204 may include pan, zoom and tiltset fields 522, 524 and 526, in which a number may be entered of tabslid for each by the user. For example, if the zoom range is from 1 to10, the user may enter a desired amount of zoom by entering a numberbetween 1 and 10. Similarly, the tilt range may be 0 to 180 degrees,where the user enters a number corresponding to the desired degree tiltfrom a vertical or horizontal reference plane. The pan range may be 0 to360 degrees, where the user enters a number corresponding to the desiredangular orientation about a vertical axis and from a zero referenceangle. Optionally, the user may be afforded a field on the screen wherenumeric values are entered to set the PZT.

FIG. 6 illustrates the map 202, on which selected nodes have beenchanged to an offline state. In FIG. 6, the nodes at 604 and 606 havebeen changed to an offline state. The communications links 608, 610 and612 have been changed to reflect the new condition of the communicationslinks as being offline. By way of example, the communications links maybe shown with red indicia to indicate the nodes are no longercommunicating with one another.

The user is presented with a redline toolbar 622. From the redlinetoolbar 622, the user may select various redline options, such asdrawing a box around a desired area by selecting icon 624. A selectedbox 620 is shown which has been drawn around a desired area. Inaddition, the user may enter text by selecting icon 626. The user mayperform freehand drawing by selecting icon 628 and then drawing afreehand line 630.

FIG. 7 illustrates the map 202 with a background blending window 702open. The background blending window 702 includes a slide bar 704 and atab 706. The user may adjust the content of the window 204 by slidingthe tab 706. At one extreme, only a roadmap is illustrated. As the tabs706 is slid along the slide bar 704, aerial photographic information isblended in with the street map and the surveillance and network devicesto illustrate a more complete geographic map with more detailedtopological information.

FIG. 8 illustrates the map 202 with an identification window 802 pulledup in connection with an individual selected surveillance device. Thewindow 802 includes a list of fields identifying attributes regardingthe individual surveillance device. The fields may also list referencedocuments that are stored in connection with the individual surveillancedevice on the GI storage. The user may gain access to an individualdocument by selecting on the document from window 802.

FIG. 9 illustrates a block diagram of a processing carried out inaccordance with an embodiment to collect, store and manage SD and NDcontent. Beginning at 902, the process stores map data for a monitoredregion in the GI storage 186. At 904, the process creates surveillancedevice related objects and network device related objects (SDR and NDRobjects) for each new SD or ND that has been added to the monitoredregion. The operation at 904 may be carried out periodically over a longperiod of time as new surveillance devices and new network devices areadded to the monitored region. Similarly, the map data stored at 902 maybe periodically updated or replaced as additional information isobtained or as alternative maps or maps sources are utilized.

At 906, the process collects SD and ND content for each SDR object andeach NDR object, respectively. The architecture of the database in theGI storage 186 utilizes a unique SDR object for each surveillance devicethat is added to the monitored region. The database architecturesimilarly maintains, in the GI storage 186, a separate NDR object foreach network device that is installed within the monitored region. Theoperation at 906 may be performed at various times over a long period oftime. For example, when an initial group of surveillance and networkdevices are installed, content related thereto may be initiallycollected, saved in the GI storage 186 and mapped to the correspondingSDR object and NDR object. By way of example only, when a surveillancecamera is mounted on a pole, an SDR object is created within the GIstorage and uniquely associated with the surveillance camera. Inaddition, position information (such as geographic coordinates) isrecorded in the GI storage and mapped to a SDR object. The positioninformation represents SD position information as it identifies alocation of the corresponding surveillance device in the monitoredregion. The position information is one example of surveillance devicecontent that may be stored in the GI storage 186. Other examples ofsurveillance device content may include position information for assets(e.g., utility poles, buildings, traffic light poles, and the like) withrespect to which surveillance devices are installed. For example, when acamera is installed on a traffic light pole, geographic coordinates maybe recorded as position information for the traffic light pole asset.The geographic coordinates of the traffic pole are stored as anothertype of surveillance device content that is uniquely mapped to the SDRobject associated with the camera. Other examples of surveillance devicecontent include surveillance device data that is collected by acorresponding surveillance device such as video, still images, motiondetection data, temperature information, and the like. Surveillancedevice content also includes surveillance device documentationdescribing the associated device, such as documentation related toinstallation, operation and maintenance of the surveillance device.Other examples of surveillance device content are described throughoutthe present application and included within the scope of surveillancedevice content. At 906, the surveillance device content may be collectedat various times throughout operation and updated within the GI storage186. At the time that content updates are added, the updated informationis mapped back to the corresponding SDR object.

At 906, the process also collects network device content for eachnetwork device within the monitored region. The network device contentmay include network device position information that identifies alocation of the corresponding network device in the monitored region.The network device content may also include asset position information,indentifying a location for a corresponding asset with respect to whicha network device is installed. The network device content may alsoinclude ND data collected by corresponding network devices, as well asND documentation describing, among other things, installation, operationand maintenance of the corresponding network device.

At 908, the SD and ND content are stored in the GI storage and mapped tothe associated SDR object and NDR object, respectively. At 910, theprocess repeatedly monitors and collects new or updates to the ND and SDspecific content. For example, at 910 the process may update videosegments or still images that are collected in connection with a camera.As another example, new or updates to the bandwidth capacity, utilizedbandwidth, signal quality, sensitivity and other network information maybe collected and stored as ND content for a particular network device.At 912, the new or updated ND or SD content are stored in the GI storage186 and mapped to the associated NDR or SDR objects. The process of FIG.9 is continuously repeated over a long period of time, such as severalmonths or years to provide historic and the most recent informationassociated with each surveillance and network device.

FIG. 10 illustrates a processing sequence carried out in accordance withan embodiment for updating content associated with surveillance devices.Beginning at 1002, the process obtains a list of surveillance deviceswithin the monitored region. At 1004, the process begins steppingthrough each surveillance device within the monitored region todetermine whether it is appropriate to perform a query to obtain newcontent for the current surveillance device. For example, with videocameras, the GIMU 180 may obtain new video segments at a predeterminedperiodic interval. Alternatively, the GIMU 180 may obtain new videosegments each time a particular camera is moved, such as zoomed in orpanned. Alternatively, new video segments may be obtained each timeanother type of triggering event occurs (e.g., another device detects atriggering event signal such as a car passing through an intersection ora particular type of event occurring). Optionally, the GIMU 180 maysubmit queries at a predetermined periodic interval. When at 1004, it isdetermined that new content should be collected in connection with thecurrent surveillance device, flow passes to 1006 where the device ID isdetermined. The video manager unit 152 manages the surveillance deviceswithin the monitored region 110 based on a unique ID associated witheach surveillance device. The IDs used by the video manager unit 152 maybe assigned by the video manager unit and may be the same as, ordifferent from, the IDs utilized by the GIMU 180. When the video managerunit 152 utilizes a separate identification than the IDs used by theGIMU 180, at 1006, the process maps the SDR object to the device IDutilized by the video manager unit 152.

At 1008, the GIMU 180 sends a query to the video manager unit 152 torequest new content (e.g., such as a most recent video segment obtainedfor the selected surveillance device). Alternatively, at 1008, the GIMU180 may directly access the SD database 162 to obtain the most recentvideo segment. As a further option, a separate SD shared space mayexist, within the SD database 162, within the GI storage 186 orelsewhere over the internet 170. The video manager unit 152 may pushvideo segments to the SD shared space and write over these videosegments periodically. The GIMU 180 may access the SD shared space toobtain the most recent video segments before such segments are writtenover. While the foregoing example is described in the context ofobtaining video content, it should be recognized that a similar processmay be followed for any type of SD content, such as still images, motiondetection information, as well as other surveillance content. At 1010,the video management unit 152 processes a query and returns the currentSD content. Alternatively, the VMU 152 may grant limited access by theGIMU 180 into the SD database 162 to directly collect SD content.Alternatively, the VMU 152 may push a selected video segment, stillimages or other surveillance information to an SD shared space inresponse to specific queries from the GIMU. The GIMU 180 may thencollect the SD content from the SD shared space once the VMU 152 haspushed the content for the desired surveillance device to this sharedspace. At 1012, the GIMU 180 stores the SD content in the GI storage 186and maps this new updated content to the SDR object for the currentsurveillance device. After the operation at 1012, flow moves along path1014. At 1016, the process increments to the next surveillance device onthe list and flow returns to 1004.

Returning to 1004, once it is determined that it is not time to querythe current surveillance device for new content, flow moves to 1018. At1018, it is determined whether all of the surveillance devices on thelist for the monitored region have been checked. If not, flow moves to1016 and the process increments to the next surveillance device. Onceall of the surveillance devices are checked, flow moves along 1020 andit returns to the overall process.

FIG. 11 illustrates a processing sequence carried out in accordance withan embodiment for updating content associated with network devices.Beginning at 1102, the process obtains a list of network devices withinthe monitored region. At 1104, the process begins stepping through eachnetwork device within the monitored region to determine whether it isappropriate to perform a query to obtain new content for the currentnetwork device. For example, the GIMU 180 may obtain new link status ata predetermined periodic interval. When at 1104, it is determined thatnew content should be collected in connection with the current networkdevice, flow passes to 1106 where the device ID is determined. The videomanager unit 152 manages the network devices within the monitored region110 based on a unique ID associated with each network device. The IDsused by the network manager unit 151 may be assigned by the manager unitand may be the same as or different from the IDs utilized by the GIMU180. When the manager unit 151 utilizes a separate identification systemthan the IDs used by the GIMU 180, at 1106, the process matches the NDor object to the device ID utilized by the network manager unit 151.

At 1108, the GIMU 180 sends a query to the network manager unit 151 torequest new content (e.g., such as a most recent signal quality,bandwidth usage, etc. for the selected network device). Alternatively,at 1108, the GIMU 180 may directly access the NW database 161 to obtainthe most recent device or link status. As a further option, a separateNW shared space may exist, within the NW database 161, within the GIstorage 186 or elsewhere over the internet 170. The network manager unit151 may push network content to the NW shared space and write over thenetwork content periodically. The GIMU 180 may access the NW sharedspace to obtain the most recent network content before such networkcontent are written over. While the foregoing example is described inthe context of obtaining network content, it should be recognized that asimilar process may be followed for any type of ND content.

At 1110, the network management unit 151 processes a query and returnsthe current ND content. Alternatively, the VMU 152 may grant limitedaccess to the GIMU 180 into the NW database 161. Alternatively, the NMU151 may be push a content to an ND shared space in response to specificqueries from the GIMU. The GIMU 180 may then collect the ND content fromthe NW shared space once the NMU 151 has pushed the content for thedesired network device to this shared space. At 1112, the GIMU 180stores the ND content in the GI storage 186 and maps this new updatedcontent to the NDR object for the current network device. After theoperation at 1112, flow moves along path 1114. At 1116, the processincrements to the next network device on the list and flow returns to1104.

Returning to 1104, once it is determined that it is not time to querythe current network device for new content, flow moves to 1118. At 1118,it is determined whether all of the network devices on the list for themonitored region have been checked. If not, flow moves to 1116 and theprocess increments to the next network device. Once all of the networkdevices are checked, flow moves along 1120 and it returns to the overallprocess.

FIG. 12 illustrates a process carried out while a user is reviewinggeographic information, device markers and network links on a graphicuser interface. Beginning at 1202, a graphical map is pulled from the GIstorage 186 and displayed for all or a portion of the monitored region.At 1204, the GIMU 180 determines which SD and ND markers and networklinks should be shown based on the position information for thesurveillance devices and network devices and the boundaries of thedisplayed region. For example, when the user has selected to view aportion of the monitored region that is only four or five blocks square,at 1204, markers and links for the surveillance and network devices,within this four or five block area, would be designated to be listed.Next, at 1206, GIMU 180 determines a current status of each of thesurveillance devices, network devices and links.

At 1208, this status information is overlayed with the markers and linksonto the geographic map. For example, referring to FIG. 3, theoperations at 1204 to 1208 identify each of the devices at nodes N12,P24, F29, P27 and F32, as well as the links therebetween. The statusinformation determined at 1206 is used to determine which color tohighlight the links between the network devices. Color may also be usedto indicate the status of a device, such as to indicate whether it isonline or offline and the like. As a further example, with reference toFIG. 4, the SD markers may include camera condition indicia 406 whichindicate the direction in which a camera is pointed as well as the fieldof view for the camera. In the example of FIG. 4, a portion of theindicia 406 have no border indicating that the camera is the type ofcamera that can be moved, such as panned, zoomed and tilted. Otherindicia 406 include a dark black border, thereby indicating that thecorresponding camera is a stationary camera that cannot be adjusted inpan, zoom or tilt.

Returning to FIG. 12, once the map, markers, links and statuses aredisplayed in an overlapped manner, the process monitors the userinterface at 1210 to determine whether the user selects one of themarkers or network links (by clicking on it or hovering over it orotherwise). At 1210, the process also determines if the user selects anarea that may include multiple markers or links. When the user selectsor tries to modify a marker, network link or area, flow moves to 1212.At 1212, the GIMU 180 obtains the SDR or NDR object for the marker, linkor area that the user has selected or wishes to modify. Next, flow movesto point B which is described further in connection with FIG. 13.

Returning to 1210, when the user does not select a marker, network linkor area, nor wish to modify one, flow moves to 1214. At 1214, it isdetermined whether the status of a surveillance device, network deviceor link has changed. When the status changes for a displayedsurveillance or network device or link, flow moves along 1216 where theoperations at 1206-1210 are repeated. When the status remains constantat 1214, flow moves to 1218. At 1218, it is determined whether the userhas changed the region that is displayed, such as when the user wishesto view a different region of interest. When the user changes the regionof interest displayed, flow moves along 1220 where a new graphical mapis obtained at 1202 for the newly selected monitored region or portionof a monitored region. After 1202, the operations of 1204-1210 arerepeated.

Returning to 1218, when the region of interest does not change, it isnext determined whether the user has selected an edit toolbar. When theuser selects the edit toolbar at 1222, the edit functions are performedat 1224 after which flow moves along 1220. The operations of FIG. 12 arecontinuously repeated to obtain new information and update the displayas the user selects various markers and network links, therebyfacilitating management of the network and surveillance devices througha geographic information portal.

FIG. 13 illustrates, in more detail, the process performed when the userwishes to select or modify an SD or ND marker, a network link or anarea. Beginning at 1302, it is first determined whether the user hasselected to view a device identity window. When Yes, flow moves to 1304where the GIMU 180 accesses the database 186 to obtain the list of SD orND content for the selected SDR or NDR object. For example, withreference to FIGS. 3 and 8, it may be determined at 1302 that the userhas selected the surveillance device P24 by clicking on the nodeassociated therewith and illustrated in FIG. 3. The GIMU 180 determinesthe SDR object associated with node P24 and obtains at 1304, the list ofSD content that has been mapped to the SDR object for node P24. At 1306,an identity window is displayed (802 in FIG. 8) that illustrates a listof the various types of surveillance device content that have been savedwithin the GI storage and mapped to the SDR object associated withcamera P24. In the example of FIG. 8, the identity window illustrates alist of attributes associated with the individual surveillance camera,as well as a list of reference documents that have been stored withinthe GI storage for the individual camera. These documents include, amongother things, documents that define the operation, performance andcapabilities of the camera, as well as documents used by variouspersonnel to install, maintain and operate the device. For example, thedocuments may include device specifications, operational parameters,maintenance information, installation instructions, repair information,and the like.

Returning to 1302, when the device identity is not selected, flow movesto 1308. At 1308, it is determined whether the user has selected to viewa video or image pop up screen. For example, when the SD device is astill or video camera, the user may click on the corresponding node(e.g., node P32 in FIG. 4). When the user selects to view an image orvideo, flow moves to 1310 where the GIMU 180 obtains video or imagesfrom the GI storage 186. Alternatively, when video or images are notstored in the GI storage 186, the GIMU 180 may request the still imagesor video segments from the video management unit 152. Optionally, theGIMU 180 may directly access the SD database 162 and pull directly fromthe SD database the desired video segment or segments. As a furtheroption, the GIMU 180 may go to an SD shared space to obtain the desiredvideo or still image. Next, at 1312, the video or image is displayed ina window. For example, as shown in FIG. 5, a video or image 510 may bedisplayed in window 512 for the camera at node P32. Thereafter, flowreturns to point A in FIG. 12.

Returning to 1308, when it is determined that the user has not selectedan image or video pop up screen, flow moves to 1314. At 1314, it isdetermined whether the user has selected to modify the status of adevice, the status of a link or to modify an area. When the user selectsto perform a modification at 1314, flow moves to 1316. At 1316, the GIMU180 updates the surveillance device or network device content with themodification. The content may be stored locally on the GI storage 186 orthe GIMU 180 may have direct access to the location at which the SD orND content is stored. When the GIMU 180 does not have direct access tothe stored content, the GIMU sends a request at 1318 to the appropriatemanager of such content. For example, when the user requests to adjustthe direction in which a camera is pointed, this modification may besent by the GIMU 180 to video manager unit 152 which then implements thepan, zoom or tilt as requested to adjust position of the camera.Optionally, when the user selects to change the status of a networkdevice, such as turning a network device On or Off or adjusting theoperation of a network link, the GIMU 180 may directly update the localND content stored in the GI storage 186 (at 1316). The GIMU 180 willalso send the request to update the network device or network link tothe network manager unit 151 which then may directly perform the updateto the status of the corresponding network device or network link. At1320, the video manager unit 152 performs a requested update, thenetwork manager unit 151 performs a requested update and the devicemanager unit 150 performs requested updates for network and surveillancedevices as well as network links. Thereafter, flow returns to point A inFIG. 12.

Returning to the decision at 1314, when it is determined that there hasbeen no selection to modify a device or a network link or an area, flowreturns to point A in FIG. 12. The operation of FIGS. 12 and 13 areiteratively performed to facilitate management of the network andsurveillance devices through a series of windows presented on thegeographic information portal displayed on the user interface as shownin FIGS. 2-8.

In accordance with the embodiments described herein, a database isprovided to facilitate management of network devices that aredistributed over a monitored region, through a geographic information(GI) portal. The database comprises map data defining a geographic mapof the monitored region, in which assets of interest are located and inwhich surveillance devices (SDs) and network devices (NDs) are installedrelative to the assets of interest. The database further comprisessurveillance device related (SDR) objects in the GI storage, whereineach of the SDR objects uniquely associated with one of the SDs. Thedatabase further comprises network device related (NDR) objects, whereineach of the NDR objects uniquely associated with one of the NDs. Thedatabase further comprises network device content mapped to the NDRobjects and surveillance device content mapped to the SDR objects.

The surveillance device content includes at least one of the following:i) SD position information regarding a location of the correspondingsurveillance device in the monitored region: ii) asset positioninformation regarding a location for the corresponding asset withrespect to which the SD is installed: iii) SD data collected by thecorresponding SD: and iv) SD documentation describing at least one ofinstallation, operation, and maintenance of the corresponding SD. Thenetwork device content includes at least one of the following: i) NDposition information regarding a location of the corresponding networkdevice in the monitored region: ii) asset position information regardinga location for the corresponding asset with respect to which the ND isinstalled: iii) ND data collected by the corresponding ND: and iv) NDdocumentation describing at least one of installation, operation, andmaintenance of the corresponding ND.

The database further comprises device markers associated with the mapdata, the device markers configured to be illustrated on the geographicmap to indicate positions of the surveillance devices relative to thegeographic map, the device markers mapped to the SDR objects. At leastone of the network and surveillance device content includes documentsand attributes that define operation, performance and capabilities ofthe corresponding network or surveillance devices. The attributesinclude device identification information, device-generated content,device-status information, device-service history. At least one of thenetwork and surveillance devices content includes documentation havingone or more of documents used by emergency services personnel, waterservices, sewage services, waste management, utilities and engineeringdocuments. At least one of the network and surveillance devices contentincludes at least one of device specific information about acorresponding type of device, device specifications, operationalparameters, maintenance information, installation instructions, andrepair information.

It is to be understood that the above description is intended to beillustrative, and not restrictive. For example, the above-describedembodiments (and/or aspects thereof) may be used in combination witheach other. In addition, many modifications may be made to adapt aparticular situation or material to the teachings of the inventionwithout departing from its scope. Dimensions, types of materials,orientations of the various components, and the number and positions ofthe various components described herein are intended to defineparameters of certain embodiments, and are by no means limiting and aremerely exemplary embodiments. Many other embodiments and modificationswithin the spirit and scope of the claims will be apparent to those ofskill in the art upon reviewing the above description. The scope of theinvention should, therefore, be determined with reference to theappended claims, along with the full scope of equivalents to which suchclaims are entitled. In the appended claims, the terms “including” and“in which” are used as the plain-English equivalents of the respectiveterms “comprising” and “wherein.” Moreover, in the following claims, theterms “first,” “second,” and “third,” etc. are used merely as labels,and are not intended to impose numerical requirements on their objects.Further, the limitations of the following claims are not written inmeans-plus-function format and are not intended to be interpreted basedon 35 U.S.C. §112, sixth paragraph, unless and until such claimlimitations expressly use the phrase “means for” followed by a statementof function void of further structure.

What is claimed is:
 1. A system to facilitate management of surveillancedevices, that are distributed over a monitored region, through ageographic information (GI) portal, comprising: GI storage to store mapdata defining a geographic map of the monitored region, in which assetsof interest are located and surveillance devices (SDs) are installedrelative to the assets of interest; a GI manager unit (GIMU) to createand store surveillance device related (SDR) objects in the GI storage,each of the SDR objects uniquely associated with one of the SDs, theGIMU mapping the SDR objects to surveillance device specific contentthat includes SD documentation containing at least two of installationinstructions, device specifications, warrantees, repair information andmaintenance information of the corresponding SD, the surveillance devicespecific content further including at least two of the following: i) SDposition information regarding a location of the correspondingsurveillance device in the monitored region; ii) asset positioninformation regarding a location for the corresponding asset withrespect to which the SD is installed; or iii) SD data collected by thecorresponding SD; a display to present a geographic map of the monitoredregion with device markers illustrated thereon, the device markersindicating positions of the surveillance devices relative to thegeographic map, the device markers mapped to the SDR objects; and a userinterface to permit a user to select from the surveillance devices bychoosing the corresponding device markers, the display displaying to theuser the SD documentation associated with the SDR object for theselected surveillance device.
 2. The system of claim 1, wherein thesurveillance device content includes documents and attributes thatdefine operation, performance and capabilities of the correspondingsurveillance devices.
 3. The system of claim 2, wherein the attributesinclude device identification information, device-generated content,device-status information, device-service history.
 4. The system ofclaim 1, wherein the SD documentation is configured to be used byemergency services, water services, sewage services, waste management,utilities and engineering personnel.
 5. The system of claim 1, whereinthe GI storage stores different layers of information including base,asset and SD layers of information, the base layer of informationincluding the map data, the asset layer of information including theasset position information, the SD layer of information including the SDdocumentation which contains device specific information about acorresponding type of device, including device specifications,maintenance information, installation instructions, and repairinformation.
 6. The system of claim 1, further comprising a SD databasethat stores SD content associated with surveillance devices installedthroughout the monitored region, and a SD manager unit that manages theSD database, the GIMU submitting a query to the SD manager unit for SDcontent associated with a selected surveillance device.
 7. The system ofclaim 6, wherein the SD manager unit communicates with the surveillancedevices installed in the monitored region, the SD manager unit collectssurveillance, status, and condition data from the surveillance devicesand recording the surveillance, status and condition data in the SDdatabase.
 8. The system of claim 1, wherein the GIMU utilizes the SDRobject for a selected surveillance device to access the surveillancedevice content.
 9. A system to facilitate management of network devices,that are distributed over a monitored region, through a geographicinformation (GI) portal, comprising: GI storage to store map datadefining a geographic map of the monitored region, in which assets ofinterest are located and network devices (NDs) are installed relative tothe assets of interest; a GI manager unit (GIMU) to create and storenetwork device related (NDR) objects in the GI storage, each of the NDRobjects uniquely associated with one of the NDs, the GIMU mapping theNDR objects to network device content that includes ND documentationcontaining at least two of installation instructions, specifications,network attributes, warrantees and maintenance information of thecorresponding ND, the network related content further including at leasttwo of the following: i) ND position information regarding a location ofthe corresponding network device in the monitored region; ii) assetposition information regarding a location for the corresponding assetwith respect to which the ND is installed; or iii) ND data collected bythe corresponding ND; a display to present a geographic map of themonitored region with device markers and network links illustratedthereon, the device markers indicating positions of the network devicesrelative to the geographic map, the network links illustratingcommunications paths between network devices, the device markers andnetwork links mapped to the NDR objects; and a user interface to permita user to select from the network devices or network links by choosingthe corresponding device markers or network links, the displaydisplaying to the user the ND documentation associated with the NDRobject for the selected network device or network link.
 10. The systemof claim 9, wherein the network device content include documents andattributes that define operation, performance and capabilities of thecorresponding network devices.
 11. The system of claim 10, wherein theattributes include device identification information, device-generatedcontent, device-status information, device-service history.
 12. Thesystem of claim 9, wherein the ND documentation is configured to be usedby emergency services, water services, sewage services, wastemanagement, utilities and engineering personnel.
 13. The system of claim9, wherein the GI storage stores different layers of informationincluding base, asset and ND layers of information, the base layer ofinformation including the map data, the asset layer of informationincluding the asset position information, the ND layer of informationincluding the ND documentation that information about a correspondingtype of network device, including device specifications, operationalparameters, maintenance information, installation instructions, repairinformation.
 14. The system of claim 9, further comprising a ND databasethat stores ND content associated with network devices installedthroughout the monitored region, and a ND manager unit that manages theND database, the GIMU submitting a query to the ND manager unit for NDcontent associated with a selected network device.
 15. The system ofclaim 14, wherein the ND manager unit communicates with the networkdevices installed in the monitored region, the ND manager unit collectscommunications, surveillance, status, and condition data from thenetwork devices and recording the communications, surveillance, statusand condition data in the ND database.
 16. The system of claim 9,wherein the GIMU utilizes the NDR object for a selected network deviceto access the network device content.
 17. The system of claim 9, whereinthe GIMU accesses a NW database which stores network device contentassociated with network devices installed throughout the monitoredregion, the network device content including attributes that defineoperation, performance and capabilities of the corresponding devices.18. The system of claim 9, wherein the GIMU communications with anetwork manager unit (NMU) that communicates with the network devicesinstalled in the monitored region, the NMU collecting network devicecontent from the network devices and recording the network devicecontent in a NW database, the GIMU requesting the network device contentfrom the NMU.
 19. The system of claim 9, wherein the network links aredisplayed as different network link indicia to indicate a status,direction of communication and a type of the correspondingcommunications path.